Question about launching with switches

Is there a switch, via the shortcut command line, that can allow you to open a specific module into read only instead of exclusive edit?
Colint - Tue Jun 15 13:27:34 EDT 2010

Re: Question about launching with switches
PDU - Wed Jun 16 01:41:03 EDT 2010

Hi,

perhaps -o READ_ONLY
(see in the help)

Pierre

Re: Question about launching with switches
llandale - Thu Jun 17 13:12:19 EDT 2010

Well, I think its a no brainer to change the meaning of double-clicks to mean 'read only' instead of 'Edit' or 'Share'. Likewise to change edit mode when you follow a link to Read Only instead of Share. Folks must then mindfully open Edit or Share, drastically reducing the frequency of locking someone else out.

Yes, command line switchs "-o READ_ONLY -O READ_ONLY" will do that, but I force that down all the clients throuts in the registry anyway.

No, I don't think its realistic to do that for a particular module, but you could deploy a post-open-module trigger and force the user to confirm desire for Edit or Share for a particular module; downgrade()ing otherwise.

  • Louie

Re: Question about launching with switches
SystemAdmin - Wed Jun 23 15:45:31 EDT 2010

Colint,

Since DOORS client installs out of the box as Open Exclusive Edit, this was VERY undesirable in our company use. ie. most users first just want to go into any module in Read Only mode anyway to ponder next step or just read etc.

We choose to Open all modules in Read Only upon beginning work. This is easily handled in the DOORS client start menu or icon->properties-target field as following example text:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe" -data 36677@servername -defopenmode READ_ONLY -defopenlinkmod READ_ONLY

Once a decision is made to perform editing in any module, it is then common knowledge of the users to use the gui->edit->edit mode-> choose shareable or choose exclusive to make changes and then save and return to read only when done or save and exit the module.

reduces the number of unwanted locked in exclusive edit by just readers.

gsdguy

Re: Question about launching with switches
llandale - Wed Jun 23 17:47:21 EDT 2010

SystemAdmin - Wed Jun 23 15:45:31 EDT 2010
Colint,

Since DOORS client installs out of the box as Open Exclusive Edit, this was VERY undesirable in our company use. ie. most users first just want to go into any module in Read Only mode anyway to ponder next step or just read etc.

We choose to Open all modules in Read Only upon beginning work. This is easily handled in the DOORS client start menu or icon->properties-target field as following example text:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe" -data 36677@servername -defopenmode READ_ONLY -defopenlinkmod READ_ONLY

Once a decision is made to perform editing in any module, it is then common knowledge of the users to use the gui->edit->edit mode-> choose shareable or choose exclusive to make changes and then save and return to read only when done or save and exit the module.

reduces the number of unwanted locked in exclusive edit by just readers.

gsdguy

Getting everyone to always use the correct shortcut is not realistic. You can modify your DOORS install procedure to include this extra step.

Put the following in some file on some common server of type .reg; perhaps named "v92_SetDefaultRead.reg"

REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Telelogic\DOORS\9.2\Config] 
"defopenmode"    =
"READ_ONLY" 
"defopenlinkmode"=
"READ_ONLY"


Run that (double click on it) when DOORS is installed.

Make another file same as above except changing "HKEY_LOCAL_MACHINE" to "HKEY_CURRENT_USER", which is used by each user when no normal folks have rights to edit the Local_Machine area of the registry.

Understand the 2nd parameter will open modules read instead of shared, when you follow a link. That's useful except that some CPS routines presume the partner has been opened Shared, and won't work until you do so.

  • Louie